Skip to content

Conversation

@HITMAN5050
Copy link
Member

Summary

This PR adds three new GitHub Issue Templates to help contributors file clear and structured issues.

Templates Added

  • 🐞 bug_report.md β€” for reporting bugs with steps to reproduce
  • πŸ’‘ feature_request.md β€” for suggesting improvements or new features
  • πŸ“ task.md β€” for small documentation or maintenance tasks

Preview

After merging, when users click "New Issue", they will see three choices:

  1. Bug report
  2. Feature request
  3. Task

Checklist

  • Frontmatter labels and assignees match existing repo labels
  • Spelling and formatting checked
  • Folder path: .github/ISSUE_TEMPLATE/
  • Tested locally β€” templates show correctly in β€œNew Issue” view

Notes

Happy to make changes if maintainers suggest improvements!

@jbampton Please review when you get a chance πŸ™‚

@HITMAN5050 HITMAN5050 requested a review from jbampton as a code owner October 14, 2025 04:04
@github-actions
Copy link
Contributor

Thanks for your first pull request! We appreciate your contribution.

@github-actions github-actions bot added the infra label Oct 14, 2025
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @HITMAN5050, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the project's issue management by introducing a set of structured GitHub Issue Templates. The primary goal is to improve the quality and clarity of incoming issues, making it easier for maintainers to understand, prioritize, and address community contributions. By providing clear guidance for bug reports, feature requests, and general tasks, this change streamlines the contribution process and fosters a more organized development workflow.

Highlights

  • New Issue Templates Added: Introduced three new GitHub Issue Templates: a bug report template, a feature request template, and a general task template. These templates aim to guide contributors in providing structured and comprehensive information when opening issues.
  • Issue Template Configuration: A config.yml file has been added to the .github/ISSUE_TEMPLATE/ directory. This configuration disables the creation of blank issues and includes a direct link to the CONTRIBUTING.md guide, encouraging contributors to review guidelines before submitting issues.
  • Standardized Issue Reporting: Each template includes specific sections tailored to its purpose, such as 'To Reproduce' for bug reports, 'Describe the solution you'd like' for feature requests, and 'Steps to complete' for tasks, ensuring consistent and actionable input from users.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with πŸ‘ and πŸ‘Ž on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

@deepsource-io
Copy link

deepsource-io bot commented Oct 14, 2025

Here's the code health analysis summary for commits 31cc26e..a7c20c0. View details on DeepSourceΒ β†—.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource Python LogoPythonβœ…Β SuccessView CheckΒ β†—
DeepSource Secrets LogoSecretsβœ…Β SuccessView CheckΒ β†—
DeepSource Shell LogoShellβœ…Β SuccessView CheckΒ β†—
DeepSource Docker LogoDockerβœ…Β SuccessView CheckΒ β†—
DeepSource JavaScript LogoJavaScriptβœ…Β SuccessView CheckΒ β†—

πŸ’‘ If you’re a repository administrator, you can configure the quality gates from the settings.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a set of GitHub issue templates for bug reports, feature requests, and tasks, which is a great step towards more structured issue reporting. The templates are well-defined, and disabling blank issues is a good practice. I've identified a couple of areas for improvement: one in the config.yml to fix a potentially broken link, and another in the task.md template to make the labels more flexible and consistent with the other templates. Overall, this is a valuable addition to the repository.

blank_issues_enabled: false
contact_links:
- name: Contribution guide
url: /CONTRIBUTING.md
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The url for a contact link must be a full URL, including the protocol (e.g., https://). The current relative path /CONTRIBUTING.md will resolve to https://github.com/CONTRIBUTING.md, which is a broken link. Please update this to the full URL of the CONTRIBUTING.md file in this repository's default branch. For example: https://github.com/<owner>/<repo>/blob/main/CONTRIBUTING.md.

---
name: Task
about: Small task or documentation update.
labels: documentation, low-priority
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The labels documentation and low-priority might be too restrictive for this template. The template is for any "Small task or documentation update," but a task might not be related to documentation or could be of higher priority. To allow for more flexibility and to maintain consistency with the other issue templates, consider using a more generic task label and adding needs-triage so that priority and other relevant labels can be assigned during the triage process.

Suggested change
labels: documentation, low-priority
labels: task, needs-triage

@HITMAN5050
Copy link
Member Author

Hello @jbampton Sir , I did't change any of other base code , but i am confuse if i not change any code then why this error comming ?

@jbampton
Copy link
Member

Hey @HITMAN5050 the failing tests are unrelated to your work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants